Docker in Production by Unknown

Author:Unknown
Language: eng
Format: mobi

You should ALWAYS use real block devices for both the data and metadata when using devicemapper driver in production setups. This is especially important when you are running a lot of containers!

You can read about all available options provided by devicemapper driver on the following link.

TIP: If you are thinking of switching from the aufs driver to the devicemapper driver, you must first save all images to separate tar files by running docker save, and once the devicemapper driver has been been picked up by Docker daemon you can easily load the saved images in by running docker load.

As you can see, the devicemapper storage driver provides an interesting container storage alternative in Docker. If you are familiar with LVM and its rich toolset, you can easily manage the Docker storage in the familiar way. However, as always there are some caveats you must keep an eye on when you decide to use this driver:

devicemapper driver requires at least basic operational knowledge of devicemapper subsystem

changing any of the devicemapper options requires stopping the Docker daemon and wiping out contents of the /var/lib/docker directory

by default the size of the container filesystem is set to 10GB as discussed earlier (you can change this via dm.basesize when the daemon starts)

expanding the size of the running container that has outgrown the configured base device size is quite laborious

you can’t easily expand the size of the image - committing a container which is bigger than its base size is not easy

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.